From: Marco Trevisan (Treviño) <mail@3v1n0.net>
Date: Mon, 16 Feb 2026 20:25:36 +0000 (+0100)
Subject: search: Use async API in search result implementation
X-Git-Tag: archive/raspbian/50.5-1+rpi1~1^2~26^2~1^2~55
X-Git-Url: https://dgit.raspbian.org/%22http://www.example.com/cgi/%22/%22http:/www.example.com/cgi/%22?a=commitdiff_plain;h=1d09da4ce4d88df091ca5b988a75b8701a3ea989;p=gnome-shell.git

search: Use async API in search result implementation

SearchResultsBase.updateSearch is an async function but we do not
implement it in the same way in GridSearchResults.

While this is not wrong per se, it makes it harder to follow the chain
and potentially to handle the errors

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/4080>
---

diff --git a/js/ui/search.js b/js/ui/search.js
index 897bae5b9..32a934f43 100644
--- a/js/ui/search.js
+++ b/js/ui/search.js
@@ -497,7 +497,7 @@ class GridSearchResults extends SearchResultsBase {
         super._onDestroy();
     }
 
-    updateSearch(...args) {
+    async updateSearch(...args) {
         if (this._notifyAllocationId)
             this.disconnect(this._notifyAllocationId);
         if (this._updateSearchLater) {
@@ -519,7 +519,7 @@ class GridSearchResults extends SearchResultsBase {
             });
         });
 
-        super.updateSearch(...args);
+        await super.updateSearch(...args);
     }
 
     _getMaxDisplayedResults() {